home *** CD-ROM | disk | FTP | other *** search
- Path: comma.rhein.de!serpens!not-for-mail
- From: mlelstv@serpens.rhein.de (Michael van Elst)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Amiga doesn`t need Planar!
- Date: 10 Feb 1996 10:41:09 +0100
- Organization: dis-
- Message-ID: <4fhp7l$kaa@serpens.rhein.de>
- References: <john.hendrikx.4coj@grafix.xs4all.nl>
- NNTP-Posting-Host: serpens.rhein.de
-
- john.hendrikx@grafix.xs4all.nl (John Hendrikx) writes:
-
- >So isn't it true that Chunky is quite useable with a lot less hardware?
-
- Obviously. I never denied that for planar hardware you need a kind of
- "planar CPU" that can deal with it.
-
- > MVE> You mean the x * 100MByte/s of memory bandwidth on the graphics card
- > MVE> is slow ?
-
- >So what is 'x'? Without it this statement could mean anything.
-
- With current cards that's something between 2 and 8.
-
- >However, the bus TO the gfx-card is slow, so doing a few extra tests'and
- >branches for each pixel plotted would not make things any slower, and thus
- >wouldn't be a big overhead, like you claimed in the first place.
-
- Again you just think about a CPU and a graphics card. But real rendering
- hardware sits on the board just like a blitter.
-
- >If the hardware limits you to some arbitrary number of colors when it comes to
- >layering displays then you can be glad that the display is Chunky as this kind
- >of display can do quite rapid layering of its own without losing any colors.
-
- A chunky display can NOT do layering of its own without losing any
- colors.
-
- >better choose carefully what hardware to use. I mean, if you require a fast
- >256 color 3d view, with a cockpit overlayed then you either chose a 8-bit
- >Chunky card, or a 9-16 bit Planar card.
-
- Of course that's not equivalent. The chunky version would need more CPU
- time for the layering while it comes automatic with the deeper (planar)
- display. Again, that has little to do with chunky vs. planar. Think
- about 16bit chunky (and that would be a 16bit _paletted_ display as with
- the planar example). You can write single bytes of a pixel and get
- exactly the same effect as with planar.
-
- >Special hardware can only do what is popular, the latest effects will still be
- >CPU based at first before they become popular, IF they become popular that is.
-
- Actually the "latest effects" will probably happen on the most popuplar
- computer.
-
- > MVE> You mean the $10 DSP that handles the audio ports ? Or the $100 DSP
- > MVE> that decodes the network video streams ?
-
- >Why not add a $80 PPC603/66 and get an overall speed boost,
-
- You mean a $80 PPC603/66 that can hardly do what the $10 DSP can do and
- that is too underpowered to do what the $100 DSP can do ?
-
- >handling video streams, or the things the OS uses the DSP for. For most users
- >this will safe them more time on overall.
-
- Not if they are interested in what the DSPs do.
-
- > MVE> Usually it is weaker than special hardware and hardly used too.
-
- >Depends on the OS. It would be hard to get a single-processor based OS to make
- >good use of multiple processors, but if it is was there right from the
- >beginning the benefits could be quite high.
-
- The best you can get is to multiply the base speed by the number of
- processors.
-
- >Tasks involving frequent Harddisk
- >access for example divide their CPU power over 3 different tasks in AmigaOS
- >already.
-
- Which would run a zilch better on multiple CPUs because these tasks
- rarely run together and rarely utilize the CPU.
-
- >And almost any task can be split over multiple CPU's with a bit of
- >forethought. But it would be hard to add now, and make decent use of it, even
- >though it is never too late to start as I think multiprocessor designs are
- >going to move into the homes real soon now.
-
- Sure. Doesn't magically make it cheaper than an equivalent faster CPU.
- The architecture of a multiprocessor isn't simple, especially when you
- go beyond 2 CPUs.
-
- >Also, why would CPU + DSP be faster at TMap + MPEG than 2 CPU's? The CPU doing
- >the TMapping might actually have time left to help with the MPEG decoding.
-
- This depends on the CPUs... usually a DSP outperforms general purpose
- CPUs in these tasks (even when DEC claims the opposite if you use Alphas).
-
- So if you want to do signal processing you better have some hardware
- that does it. If you want a more flexible solution then you might start
- with multiple CPUs, but don't expect it to be cheap.
-
- >They will be stored one by one in the pattern buffer, maybe storing a few in
- >registers before writing them to the pattern buffer, but the loop which
- >calculates the pixels will clearly be working at one pixel at the time.
-
- Read below.
-
- > MVE> pixels might be computed individually but these are hardly _drawn_
- > MVE> individually.
-
- >"Drawn" to me means writing them to memory. For me the C2P step is not the
- >thing which draws the scene to the screen, instead the TMapping routine which
- >builds the Chunky buffer is the thing that draws them.
-
- What chunky buffer ? :)
-
- >For Planar the hardware determines how cool the effects can be, and determines
- >the maximum speed as well. The CPU is not involved.
-
- Why not ?
-
- >hardware speeds and CPU speeds of the same age. The speed difference is so big
- >that the CPU can afford to do a complete C2P conversion to get new cool effects
- >to be used with the old planar system.
-
- And that's what you think about graphics systems all the time.
- --
- Michael van Elst
-
- Internet: mlelstv@serpens.rhein.de
- "A potential Snark may lurk in every tree."
-